Add an option to cmsTraceFunction to abort with non-zero exit code on first breakpoint#20
Conversation
|
A new Pull Request was created by @makortel for branch master. @akritkbehera, @cmsbuild, @iarspider, @smuzaffar can you please review it and eventually sign? Thanks. |
|
cms-bot internal usage |
|
@cmsbuild, please test |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b8ce3a/47824/summary.html Comparison SummarySummary:
|
|
test parameters:
|
|
@cmsbuild, please test Let's see if this works as I expect |
|
+1 Summary: https://cmssdt.cern.ch/SDT/jenkins-artifacts/pull-request-integration/PR-b8ce3a/47826/summary.html Comparison SummarySummary:
|
|
The |
|
+externals |
|
This pull request is fully signed and it will be integrated in one of the next master IBs (tests are also fine). This pull request will now be reviewed by the release team before it's merged. @ftenchini, @sextonkennedy, @mandrenguyen (and backports should be raised in the release meeting by the corresponding L2) |
In the context of cms-sw/cmssw#46002, following discussion in core software meeting last week this PR adds
--abortoption tocmsTraceFunctionto terminate the trace with non-zero exit code on the first function breakpoint. This option should make it easier to catch the problems in DEVEL IBs (or wherever we end up using the tracing) without separate log parsing.Resolves cms-sw/framework-team#1526